Reviewing or Modifying View Properties

Sometimes you may want to look at the values and properties originally used to create a view. Reviewing this information may help you understand the behavior of changes within the view or the views that have been derived from it. Also, if you have access rights to do so, you may be able to modify view properties as well.

To view or modify view properties, select StarTeam > View > Properties. The View Properties dialog box opens.

The View Properties dialog box consists of the following tabs:

Tab Information/Options
Name
  • Name and description of the view
  • Who created the view and when it was created (read-only)
  • Whether the items are set to branch on change
  • Whether a central or a per folder repository is being used
  • Working folder path

Note: Your access rights determine which items you can change.

Hierarchy Review the list of views for this project and their relationship to one another.
Type
  • View type.
  • Whether the view is a root, branching, non-derived, or a reference view.
  • For branching views, whether the original default was Branch All or Branch None.
  • Parent view on which this view was based.
  • Parent configuration used to create this view.
View Compare Merge

For Pulse Code Review.

  • Enforce that all code be reviewed prior to committing a Change Package:

    On the Target View where Change Packages will be committed, select Allow VCM Commits only when Code review has been approved.

    Once this is done, all commits (whether PROMOTE, REBASE or REPLICATE) to this view will be automatically saved in an uncommitted state and a Pulse Code Review will be created for each saved Change Package.

    The code will need to go through the standard pulse review process until approved.

    The VCM Commit button will only be enabled if all other standard VCM commit requirements are met, and the pulse code review is approved.

    In the event that the pulse code review is abandoned, the VCM Commit button will be enabled provided that all other standard VCM commit requirements are met, but only if a StarTeam administrator attempts to commit this VCM session.

  • Prevent file check ins:

    Select Enforce VCM Commits only.

    You can exclude either individual users or groups from this rule.